Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d60c1db582510e50b1056eb999cafc0c08925ec9463f09cd543468f71e316d4b

Tx prefix hash: 620f4e1f615b9f28ed4db16241a6d14d0626fba78b9395343ac3628b4a6a8c50
Tx public key: 105db07ea7d2a2f85009af8f59ade9e1a92138e31e41a0b7422b20c19ba370b0
Timestamp: 1710421886 Timestamp [UCT]: 2024-03-14 13:11:26 Age [y:d:h:m:s]: 01:017:20:27:29
Block: 978166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273717 RingCT/type: yes/0
Extra: 01105db07ea7d2a2f85009af8f59ade9e1a92138e31e41a0b7422b20c19ba370b002110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 418854c7ae2a7418e3fbeada70ea37060796d6274325057cff6c33e7f711ad06 0.600000000000 1438183 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": 978176, "vin": [ { "gen": { "height": 978166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "418854c7ae2a7418e3fbeada70ea37060796d6274325057cff6c33e7f711ad06" } } ], "extra": [ 1, 16, 93, 176, 126, 167, 210, 162, 248, 80, 9, 175, 143, 89, 173, 233, 225, 169, 33, 56, 227, 30, 65, 160, 183, 66, 43, 32, 193, 155, 163, 112, 176, 2, 17, 0, 0, 0, 7, 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