Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 737d94d99383d2f3d51528ba9be92881c5d63cafd6af62b2b5af2c07983b1bc2

Tx prefix hash: f1d3c067cb642cba5ea1a75ef7895116054a775c1ce336c48f649f4afb062bc4
Tx public key: 4b9501fff3646ddc8a473437bd5eb34f3221b8fa8abc0263f8015cf3f94b47ea
Timestamp: 1723914647 Timestamp [UCT]: 2024-08-17 17:10:47 Age [y:d:h:m:s]: 00:268:05:40:04
Block: 1090013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191597 RingCT/type: yes/0
Extra: 014b9501fff3646ddc8a473437bd5eb34f3221b8fa8abc0263f8015cf3f94b47ea02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3199146044a8d56874a6a033f45470364ce8e06b8ade8be9421d48283579b684 0.600000000000 1564636 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": 1090023, "vin": [ { "gen": { "height": 1090013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3199146044a8d56874a6a033f45470364ce8e06b8ade8be9421d48283579b684" } } ], "extra": [ 1, 75, 149, 1, 255, 243, 100, 109, 220, 138, 71, 52, 55, 189, 94, 179, 79, 50, 33, 184, 250, 138, 188, 2, 99, 248, 1, 92, 243, 249, 75, 71, 234, 2, 17, 0, 0, 0, 4, 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