Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdf88fe7a8cf7b3f36a48ad3f0602d32152722297d9efd4e423c649fde41684f

Tx prefix hash: 84bcb4138f76c802f671f227b0bef743d4f7f1f45058ecfd46a14068f6c9eb1e
Tx public key: 4f16f0f9e5de27fd4f6b755783c72a234df75e1f4b9dfe6880d4d24a2db93c2d
Timestamp: 1725844964 Timestamp [UCT]: 2024-09-09 01:22:44 Age [y:d:h:m:s]: 00:059:11:49:20
Block: 1106011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42537 RingCT/type: yes/0
Extra: 014f16f0f9e5de27fd4f6b755783c72a234df75e1f4b9dfe6880d4d24a2db93c2d021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 930827fd443761cc702650fc068a0e144d0f6174c3440af90098211a89e82297 0.600000000000 1583554 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": 1106021, "vin": [ { "gen": { "height": 1106011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "930827fd443761cc702650fc068a0e144d0f6174c3440af90098211a89e82297" } } ], "extra": [ 1, 79, 22, 240, 249, 229, 222, 39, 253, 79, 107, 117, 87, 131, 199, 42, 35, 77, 247, 94, 31, 75, 157, 254, 104, 128, 212, 210, 74, 45, 185, 60, 45, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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