Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a90dbe80e3c5f092b7dc80b7193cac50e657f565b3d5843dd7b71e0aa113028

Tx prefix hash: db4c0227c527e26a81a6836746cd72cc9a59700c8b69d481499e57dcc7bbd523
Tx public key: b3d09be464ea6e76965af41959391b153bc881039626f49a7d9c838c64f0c82e
Timestamp: 1710213966 Timestamp [UCT]: 2024-03-12 03:26:06 Age [y:d:h:m:s]: 00:348:03:45:29
Block: 976435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248896 RingCT/type: yes/0
Extra: 01b3d09be464ea6e76965af41959391b153bc881039626f49a7d9c838c64f0c82e02110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 455c1f6c0582b7981f25d773ef2ea72e7ad13789b08f66fd313b534215d7b0e9 0.600000000000 1436430 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": 976445, "vin": [ { "gen": { "height": 976435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "455c1f6c0582b7981f25d773ef2ea72e7ad13789b08f66fd313b534215d7b0e9" } } ], "extra": [ 1, 179, 208, 155, 228, 100, 234, 110, 118, 150, 90, 244, 25, 89, 57, 27, 21, 59, 200, 129, 3, 150, 38, 244, 154, 125, 156, 131, 140, 100, 240, 200, 46, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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