Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19d75a1af8db41cf7adb4402f747dc0e403f19b3c4bbf4aa592bfb40b40725e2

Tx prefix hash: 9d1b396eaeb22ae15992592073ce29514b186cd9ba72380da11e7e0e55f3cf01
Tx public key: f2e02b996f71a23dfedc755e8c419170e82d72016c686da99bb746617d686b9a
Timestamp: 1712029062 Timestamp [UCT]: 2024-04-02 03:37:42 Age [y:d:h:m:s]: 00:283:23:35:42
Block: 991436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203306 RingCT/type: yes/0
Extra: 01f2e02b996f71a23dfedc755e8c419170e82d72016c686da99bb746617d686b9a0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a473f54d4049a95fb42e9db208dca2f4e5e6b176dfdce1d8ba199d6457bd2707 0.600000000000 1451772 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": 991446, "vin": [ { "gen": { "height": 991436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a473f54d4049a95fb42e9db208dca2f4e5e6b176dfdce1d8ba199d6457bd2707" } } ], "extra": [ 1, 242, 224, 43, 153, 111, 113, 162, 61, 254, 220, 117, 94, 140, 65, 145, 112, 232, 45, 114, 1, 108, 104, 109, 169, 155, 183, 70, 97, 125, 104, 107, 154, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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