Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d7adc30864fa754e99d117134fe23b73788398c8b1236b8d4472eef6016edb1

Tx prefix hash: 0f08a122ca4d9a819e9d72ee5771bd62b641fe7bdc6755d19482f80f54e6b75f
Tx public key: 19f9d384858226bf7c21e1248a6d8faae8e8bdaa6475802b178fdd2422f54d62
Timestamp: 1715560588 Timestamp [UCT]: 2024-05-13 00:36:28 Age [y:d:h:m:s]: 00:186:02:08:48
Block: 1020778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133164 RingCT/type: yes/0
Extra: 0119f9d384858226bf7c21e1248a6d8faae8e8bdaa6475802b178fdd2422f54d62021100000002c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7cbda0f1e08550327ea8e824d9efc329b7909efa3cff8aec10a26f4dece2ee3 0.600000000000 1484871 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": 1020788, "vin": [ { "gen": { "height": 1020778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7cbda0f1e08550327ea8e824d9efc329b7909efa3cff8aec10a26f4dece2ee3" } } ], "extra": [ 1, 25, 249, 211, 132, 133, 130, 38, 191, 124, 33, 225, 36, 138, 109, 143, 170, 232, 232, 189, 170, 100, 117, 128, 43, 23, 143, 221, 36, 34, 245, 77, 98, 2, 17, 0, 0, 0, 2, 197, 69, 41, 96, 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