Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0374136527d8f4cf28307a915f6a1f4651e76ce8d278db1b6da591a85ce90472

Tx prefix hash: ccc73699ff03d8d16422bf3d592261d2fd2189a1b4fec0c5dfb8507c885b2831
Tx public key: 402031107213b2237ce17eb9ddae44c0f8f79d09e49cd9c4c527b4ebed8ad2d1
Timestamp: 1729087482 Timestamp [UCT]: 2024-10-16 14:04:42 Age [y:d:h:m:s]: 01:024:10:21:53
Block: 1132914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275808 RingCT/type: yes/0
Extra: 01402031107213b2237ce17eb9ddae44c0f8f79d09e49cd9c4c527b4ebed8ad2d102110000000d3cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd84f8338e4a8b495ce0a9d1134116dd2a35809a256092940718bca30abc2914 0.600000000000 1615945 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": 1132924, "vin": [ { "gen": { "height": 1132914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd84f8338e4a8b495ce0a9d1134116dd2a35809a256092940718bca30abc2914" } } ], "extra": [ 1, 64, 32, 49, 16, 114, 19, 178, 35, 124, 225, 126, 185, 221, 174, 68, 192, 248, 247, 157, 9, 228, 156, 217, 196, 197, 39, 180, 235, 237, 138, 210, 209, 2, 17, 0, 0, 0, 13, 60, 208, 252, 6, 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