Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0552b6876a482e7b8b5a07e88ff93b9e192b733b2a9cf84ceaa99a2623e74d8

Tx prefix hash: f7daaa893c915bcdd5d3ae4080d791ce98cdea37da18ad3b348b0e87dea5d1ef
Tx public key: 856699573ecb2ae093978289d6c023dcc5f3c6fa5d1dffd4945b2527d275798e
Timestamp: 1650087984 Timestamp [UCT]: 2022-04-16 05:46:24 Age [y:d:h:m:s]: 03:199:03:57:19
Block: 481195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 920656 RingCT/type: yes/0
Extra: 01856699573ecb2ae093978289d6c023dcc5f3c6fa5d1dffd4945b2527d275798e0211000000044da16a3a000000000000000000

1 output(s) for total of 15.617137877000 dcy

stealth address amount amount idx
00: d021e8ce05332c4aff2a5eb734ceeb93d4a17c271f84ccc482953f925decd329 15.617137877000 902410 of 0

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": 481205, "vin": [ { "gen": { "height": 481195 } } ], "vout": [ { "amount": 15617137877, "target": { "key": "d021e8ce05332c4aff2a5eb734ceeb93d4a17c271f84ccc482953f925decd329" } } ], "extra": [ 1, 133, 102, 153, 87, 62, 203, 42, 224, 147, 151, 130, 137, 214, 192, 35, 220, 197, 243, 198, 250, 93, 29, 255, 212, 148, 91, 37, 39, 210, 117, 121, 142, 2, 17, 0, 0, 0, 4, 77, 161, 106, 58, 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