Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb55063f3c1cd26bdf83afadbdcdb20b94ac51f73580020d2aef14c8200bad65

Tx prefix hash: f583a96d522f19a3997cca8976999e8107b757fc19ca03269b9390a3cf65680f
Tx public key: 4b9e45d2e1e86cc1349988381ce3e366f916d52765ba7190d20f5a0a94f8eb0f
Timestamp: 1633268438 Timestamp [UCT]: 2021-10-03 13:40:38 Age [y:d:h:m:s]: 03:161:08:22:00
Block: 345857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 892110 RingCT/type: yes/0
Extra: 014b9e45d2e1e86cc1349988381ce3e366f916d52765ba7190d20f5a0a94f8eb0f02110000000ef60c5d7e000000000000000000

1 output(s) for total of 43.856363309000 dcy

stealth address amount amount idx
00: 1e506035abaa50eb62723412facc2f8b7ba87e9e4bdeb5d7b5a1ac3859289592 43.856363309000 709397 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": 345867, "vin": [ { "gen": { "height": 345857 } } ], "vout": [ { "amount": 43856363309, "target": { "key": "1e506035abaa50eb62723412facc2f8b7ba87e9e4bdeb5d7b5a1ac3859289592" } } ], "extra": [ 1, 75, 158, 69, 210, 225, 232, 108, 193, 52, 153, 136, 56, 28, 227, 227, 102, 249, 22, 213, 39, 101, 186, 113, 144, 210, 15, 90, 10, 148, 248, 235, 15, 2, 17, 0, 0, 0, 14, 246, 12, 93, 126, 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