Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9320c38a8881c299999ff6ba2dbceed6614ee1938efaf1827e5c2baf403d0612

Tx prefix hash: 81e9f08978b21e2fadfe4227883032f7ae765049ff00a1060e94bde0d3eefe45
Tx public key: 13a48bb72dfd691ee2d7905d63ea86e8bb258b37a9826bc69d7e203bd1ebe7d2
Timestamp: 1711206115 Timestamp [UCT]: 2024-03-23 15:01:55 Age [y:d:h:m:s]: 01:067:07:00:53
Block: 984672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309091 RingCT/type: yes/0
Extra: 0113a48bb72dfd691ee2d7905d63ea86e8bb258b37a9826bc69d7e203bd1ebe7d202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b22f2ee907fe4147c13badd2de36c96a5cc2f2bafbd1c2740e3b4a6bdfc0f18 0.600000000000 1444845 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": 984682, "vin": [ { "gen": { "height": 984672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b22f2ee907fe4147c13badd2de36c96a5cc2f2bafbd1c2740e3b4a6bdfc0f18" } } ], "extra": [ 1, 19, 164, 139, 183, 45, 253, 105, 30, 226, 215, 144, 93, 99, 234, 134, 232, 187, 37, 139, 55, 169, 130, 107, 198, 157, 126, 32, 59, 209, 235, 231, 210, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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