Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a1fd8d11cd2cec5325c60176891f132154ba0ed37728f3ebb3fc9aad204fdd2

Tx prefix hash: 2da3bddb490c1db18cf687e6f7cb14f4edaa982d7bdc7a6f6406c538e778b3b8
Tx public key: 96c53ebac58b0caf1b73ac27b42998b0f9d131ea720a17e90c8d5076e8133dc0
Timestamp: 1728490784 Timestamp [UCT]: 2024-10-09 16:19:44 Age [y:d:h:m:s]: 00:179:18:59:08
Block: 1127948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128281 RingCT/type: yes/0
Extra: 0196c53ebac58b0caf1b73ac27b42998b0f9d131ea720a17e90c8d5076e8133dc002110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc2fba67f322a574a8c897abafa5a2153b6d44b081282ef993259c5f2a842564 0.600000000000 1610763 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": 1127958, "vin": [ { "gen": { "height": 1127948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc2fba67f322a574a8c897abafa5a2153b6d44b081282ef993259c5f2a842564" } } ], "extra": [ 1, 150, 197, 62, 186, 197, 139, 12, 175, 27, 115, 172, 39, 180, 41, 152, 176, 249, 209, 49, 234, 114, 10, 23, 233, 12, 141, 80, 118, 232, 19, 61, 192, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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