Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4defd3505b32c77fc2621cfd31d71add3004bdff6986058cda31367a45cb6f69

Tx prefix hash: 255a440070b37d1852543c1f52a60d79f0cb7c7940c403e4e7c95223c65fad0b
Tx public key: 8df58c2291dad149c8131f3b54fb65e63016ec53f7df5c1b4a2d979a1ecdf3f0
Timestamp: 1578945445 Timestamp [UCT]: 2020-01-13 19:57:25 Age [y:d:h:m:s]: 04:320:00:52:14
Block: 44931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118148 RingCT/type: yes/0
Extra: 018df58c2291dad149c8131f3b54fb65e63016ec53f7df5c1b4a2d979a1ecdf3f002110000000a4ac5aa02000000000000000000

1 output(s) for total of 435.667480214000 dcy

stealth address amount amount idx
00: 3902aa0d90699c50861f7b2a4b1fe3e421c414976bcabc1e956c3051bd1f5887 435.667480214000 81929 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": 44941, "vin": [ { "gen": { "height": 44931 } } ], "vout": [ { "amount": 435667480214, "target": { "key": "3902aa0d90699c50861f7b2a4b1fe3e421c414976bcabc1e956c3051bd1f5887" } } ], "extra": [ 1, 141, 245, 140, 34, 145, 218, 209, 73, 200, 19, 31, 59, 84, 251, 101, 230, 48, 22, 236, 83, 247, 223, 92, 27, 74, 45, 151, 154, 30, 205, 243, 240, 2, 17, 0, 0, 0, 10, 74, 197, 170, 2, 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