Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07fbb21fe9205508d298b752f07959ab5b5d7dd1515d197a4ec963716d370fc4

Tx prefix hash: bd6924a0c2954467620e774023efae57d0e7c0606660948aa945d817b4183cd7
Tx public key: dd3c9f739a5c42a2c9ad13d7481adb3dcc1ae925241e6336d897f51dc06917be
Timestamp: 1751247605 Timestamp [UCT]: 2025-06-30 01:40:05 Age [y:d:h:m:s]: 00:216:13:27:16
Block: 1315527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152878 RingCT/type: yes/0
Extra: 01dd3c9f739a5c42a2c9ad13d7481adb3dcc1ae925241e6336d897f51dc06917be0211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 256bb5d113544fec66fb135fd2714607a407bd7159d2de03a9dab3ceb5167b3e 0.600000000000 1803182 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": 1315537, "vin": [ { "gen": { "height": 1315527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "256bb5d113544fec66fb135fd2714607a407bd7159d2de03a9dab3ceb5167b3e" } } ], "extra": [ 1, 221, 60, 159, 115, 154, 92, 66, 162, 201, 173, 19, 215, 72, 26, 219, 61, 204, 26, 233, 37, 36, 30, 99, 54, 216, 151, 245, 29, 192, 105, 23, 190, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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