Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: fcf936d23f79bd50328c20f5207ea26b85ab8e575ca6e220314f4d512482d4cb

Tx prefix hash: e76859ea827eb7d7e7da14f41fac3df3912b4dee85c0c39eecdc597d027fad6f
Tx public key: f83c2971a3dd9a238cf77fa113aa91093949cbd4268fbec1bc249016ab2e7890
Timestamp: 1733258199 Timestamp [UCT]: 2024-12-03 20:36:39 Age [y:d:h:m:s]: 00:134:14:04:16
Block: 1167368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95998 RingCT/type: yes/0
Extra: 01f83c2971a3dd9a238cf77fa113aa91093949cbd4268fbec1bc249016ab2e7890021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4daf70038d470bdf8e573ab220bc42b75b599b6da2ef70e8c66b04e49e10e3a2 0.600000000000 1653063 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1167378, "vin": [ { "gen": { "height": 1167368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4daf70038d470bdf8e573ab220bc42b75b599b6da2ef70e8c66b04e49e10e3a2" } } ], "extra": [ 1, 248, 60, 41, 113, 163, 221, 154, 35, 140, 247, 127, 161, 19, 170, 145, 9, 57, 73, 203, 212, 38, 143, 190, 193, 188, 36, 144, 22, 171, 46, 120, 144, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8