Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af1ab6e587ca522c529ce54bf43efe69d392d245ce37889bca10d47dc8e82a44

Tx prefix hash: 5caa9cecd8905673cee00ab3f934e1a007ed8baa9aed6f59d69da20d107729ae
Tx public key: 262fa7586ae08535e4fcfcf35431f2d9f8f8866dc64f2a8f65a4942170b51f00
Timestamp: 1706590467 Timestamp [UCT]: 2024-01-30 04:54:27 Age [y:d:h:m:s]: 01:076:09:24:05
Block: 946362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315679 RingCT/type: yes/0
Extra: 01262fa7586ae08535e4fcfcf35431f2d9f8f8866dc64f2a8f65a4942170b51f000211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc400d8696737da2c714dff28651ebc86d759d9fd9bf6552d797bc3bf33e056d 0.600000000000 1404694 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": 946372, "vin": [ { "gen": { "height": 946362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc400d8696737da2c714dff28651ebc86d759d9fd9bf6552d797bc3bf33e056d" } } ], "extra": [ 1, 38, 47, 167, 88, 106, 224, 133, 53, 228, 252, 252, 243, 84, 49, 242, 217, 248, 248, 134, 109, 198, 79, 42, 143, 101, 164, 148, 33, 112, 181, 31, 0, 2, 17, 0, 0, 0, 2, 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