Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc04e04eb1685f2dbc9b9a65f0baebccbd74b526c1e5300946eec801b41dd054

Tx prefix hash: 10f7241fc3ece3bf66aeb7c3d9c0393e087d57833d0d6c75272337c9ef772c66
Tx public key: 46a3b6b51306d4e17d4060ae2d5fce98ed3dbdce288f48ea60a3ad10f569269f
Timestamp: 1578656188 Timestamp [UCT]: 2020-01-10 11:36:28 Age [y:d:h:m:s]: 05:054:23:57:55
Block: 42596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1189328 RingCT/type: yes/0
Extra: 0146a3b6b51306d4e17d4060ae2d5fce98ed3dbdce288f48ea60a3ad10f569269f0211000000084ac5aa02000000000000000000

1 output(s) for total of 443.468333033000 dcy

stealth address amount amount idx
00: 46b15a7be4a17a3c35ada25ba34b4902c0fb926873e57da745a4f1741c2faf6a 443.468333033000 76797 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": 42606, "vin": [ { "gen": { "height": 42596 } } ], "vout": [ { "amount": 443468333033, "target": { "key": "46b15a7be4a17a3c35ada25ba34b4902c0fb926873e57da745a4f1741c2faf6a" } } ], "extra": [ 1, 70, 163, 182, 181, 19, 6, 212, 225, 125, 64, 96, 174, 45, 95, 206, 152, 237, 61, 189, 206, 40, 143, 72, 234, 96, 163, 173, 16, 245, 105, 38, 159, 2, 17, 0, 0, 0, 8, 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