Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4d256c20dbedffe4ab05614ef72fab6b434a9818ade2286aeb1fb6d76d51aa6

Tx prefix hash: d83ee4789e0fde8d5a5c01ec2682075334f9b33217df1e0feb9b0c28d2bb995b
Tx public key: cc2416c63cfd752b6087d28ab7cc2ebf74ded9621823a290c9e1f5091122c081
Timestamp: 1739648400 Timestamp [UCT]: 2025-02-15 19:40:00 Age [y:d:h:m:s]: 00:267:11:57:39
Block: 1219976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188961 RingCT/type: yes/0
Extra: 01cc2416c63cfd752b6087d28ab7cc2ebf74ded9621823a290c9e1f5091122c081021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b81c79d067a2b171c43d9f51dab97b281a8b0800e645cda5b7c9f15f006b206 0.600000000000 1706813 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": 1219986, "vin": [ { "gen": { "height": 1219976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b81c79d067a2b171c43d9f51dab97b281a8b0800e645cda5b7c9f15f006b206" } } ], "extra": [ 1, 204, 36, 22, 198, 60, 253, 117, 43, 96, 135, 210, 138, 183, 204, 46, 191, 116, 222, 217, 98, 24, 35, 162, 144, 201, 225, 245, 9, 17, 34, 192, 129, 2, 17, 0, 0, 0, 4, 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