Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e519bf0b6c7b0781fad9c6440677331bc5bbc013c6fa697496b4c1fdcf42484d

Tx prefix hash: cc41e60b38a3d695d2ad6d4bd9bbdec03d189cfe240f1ba1014e666a0ed6839c
Tx public key: a6b9a0ec4416648b2e3fdfae0407aa67b8f5f5f16977edc2cd9a83737a666b9a
Timestamp: 1577701259 Timestamp [UCT]: 2019-12-30 10:20:59 Age [y:d:h:m:s]: 04:335:19:56:42
Block: 34935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129145 RingCT/type: yes/0
Extra: 01a6b9a0ec4416648b2e3fdfae0407aa67b8f5f5f16977edc2cd9a83737a666b9a02110000021bc3a1a09f000000000000000000

1 output(s) for total of 470.161104388000 dcy

stealth address amount amount idx
00: 93232c9d53c62d6ea5f378217341bcc2d676986902cc16efd134f938acc7306d 470.161104388000 58852 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": 34945, "vin": [ { "gen": { "height": 34935 } } ], "vout": [ { "amount": 470161104388, "target": { "key": "93232c9d53c62d6ea5f378217341bcc2d676986902cc16efd134f938acc7306d" } } ], "extra": [ 1, 166, 185, 160, 236, 68, 22, 100, 139, 46, 63, 223, 174, 4, 7, 170, 103, 184, 245, 245, 241, 105, 119, 237, 194, 205, 154, 131, 115, 122, 102, 107, 154, 2, 17, 0, 0, 2, 27, 195, 161, 160, 159, 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