Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3f962d8a31dc152117a2a490c111841b0b5c89924ec2b71dd0b11ce53f15008

Tx prefix hash: 3d1b13c1f96bfbb0fd58c170670256e5488e8eda3a094658d32821a5e4a9c76b
Tx public key: 5d6d7be50cbe7deb6f9696cbcb2c300a8d364553f2a938fe49c50370e4ce2fb9
Timestamp: 1710251212 Timestamp [UCT]: 2024-03-12 13:46:52 Age [y:d:h:m:s]: 01:064:00:54:19
Block: 976748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306775 RingCT/type: yes/0
Extra: 015d6d7be50cbe7deb6f9696cbcb2c300a8d364553f2a938fe49c50370e4ce2fb902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b605bf50199fb2d9b8003ad5e4dc23677c76eb4a15c6baa7b87546054d43edd 0.600000000000 1436743 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": 976758, "vin": [ { "gen": { "height": 976748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b605bf50199fb2d9b8003ad5e4dc23677c76eb4a15c6baa7b87546054d43edd" } } ], "extra": [ 1, 93, 109, 123, 229, 12, 190, 125, 235, 111, 150, 150, 203, 203, 44, 48, 10, 141, 54, 69, 83, 242, 169, 56, 254, 73, 197, 3, 112, 228, 206, 47, 185, 2, 17, 0, 0, 0, 3, 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