Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 288e5a514ba8e93e856cab853398e1de380d592163dbd897da09c6fbdb906978

Tx prefix hash: d7b034c95d2ddf6959be84acc4dada84ef07a3520fa251d05623d5d38053c703
Tx public key: 0b2e76a30c3d896f42cbce8277e8e10eea9ec3d1d55646f79cc497ab694f6c1b
Timestamp: 1578483076 Timestamp [UCT]: 2020-01-08 11:31:16 Age [y:d:h:m:s]: 05:128:05:58:58
Block: 41174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1241721 RingCT/type: yes/0
Extra: 010b2e76a30c3d896f42cbce8277e8e10eea9ec3d1d55646f79cc497ab694f6c1b0211000000074ac5aa02000000000000000000

1 output(s) for total of 448.305732019000 dcy

stealth address amount amount idx
00: f86d19974af5bc8997f4f88ea66e63c281f3196673227d0765ce6f70958d82d7 448.305732019000 73092 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": 41184, "vin": [ { "gen": { "height": 41174 } } ], "vout": [ { "amount": 448305732019, "target": { "key": "f86d19974af5bc8997f4f88ea66e63c281f3196673227d0765ce6f70958d82d7" } } ], "extra": [ 1, 11, 46, 118, 163, 12, 61, 137, 111, 66, 203, 206, 130, 119, 232, 225, 14, 234, 158, 195, 209, 213, 86, 70, 247, 156, 196, 151, 171, 105, 79, 108, 27, 2, 17, 0, 0, 0, 7, 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