Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 260e66cb4102a2a5dcf6e6eaa701167f5decb349f37c3f21561a0b669a77c4ec

Tx prefix hash: 79e7ce1ab6f6d16b7a838a17ebb64916e8030f9c4c518c9992ef7f756da2d1b5
Tx public key: 48dbad9b6d45da75e572351e30b44b26bf75a7313ef1b073252fe0e354baaa23
Timestamp: 1736004700 Timestamp [UCT]: 2025-01-04 15:31:40 Age [y:d:h:m:s]: 00:351:02:40:14
Block: 1190113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248492 RingCT/type: yes/0
Extra: 0148dbad9b6d45da75e572351e30b44b26bf75a7313ef1b073252fe0e354baaa23021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 461e5c231d97067667737ceba1d26a004b55945c1c5c5f8974b7e4cd495581d7 0.600000000000 1676628 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": 1190123, "vin": [ { "gen": { "height": 1190113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "461e5c231d97067667737ceba1d26a004b55945c1c5c5f8974b7e4cd495581d7" } } ], "extra": [ 1, 72, 219, 173, 155, 109, 69, 218, 117, 229, 114, 53, 30, 48, 180, 75, 38, 191, 117, 167, 49, 62, 241, 176, 115, 37, 47, 224, 227, 84, 186, 170, 35, 2, 17, 0, 0, 0, 2, 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