Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9b4c4e63b2cc8577ece45f5733411227db356e47b377a951c1084f80c3efc35

Tx prefix hash: 26ecd8725ac6ef7e36df6754c2f2232c8a3d240abd83dc9d6ac5a856f7fc167d
Tx public key: c30c49a0512608711d147ff8d4fb2ffecf28a680fd892656fed1a006731f3a62
Timestamp: 1641089924 Timestamp [UCT]: 2022-01-02 02:18:44 Age [y:d:h:m:s]: 02:359:18:26:46
Block: 408547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 775283 RingCT/type: yes/0
Extra: 01c30c49a0512608711d147ff8d4fb2ffecf28a680fd892656fed1a006731f3a6202110000000e0bc544d7000000000000000000

1 output(s) for total of 27.184073263000 dcy

stealth address amount amount idx
00: 8db916c7d6eacdd934c2467c494837419aebe159002048c9db8a0bc1e71e11bf 27.184073263000 810646 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": 408557, "vin": [ { "gen": { "height": 408547 } } ], "vout": [ { "amount": 27184073263, "target": { "key": "8db916c7d6eacdd934c2467c494837419aebe159002048c9db8a0bc1e71e11bf" } } ], "extra": [ 1, 195, 12, 73, 160, 81, 38, 8, 113, 29, 20, 127, 248, 212, 251, 47, 254, 207, 40, 166, 128, 253, 137, 38, 86, 254, 209, 160, 6, 115, 31, 58, 98, 2, 17, 0, 0, 0, 14, 11, 197, 68, 215, 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