Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e254355ed109e1f3a6d2c4aaea6b4abcb451ea532d8ebc81ba618c662ac2e9ac

Tx prefix hash: 5dfc0f248f8273e47c812c0bcf930446dcbfee792b8225993e0c0654f24e6cd7
Tx public key: e920e61bc7546f4e05758327f5e8fe7a84de45e79e2adb454f9d537d230c1d94
Timestamp: 1576511146 Timestamp [UCT]: 2019-12-16 15:45:46 Age [y:d:h:m:s]: 04:338:07:01:00
Block: 27915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128076 RingCT/type: yes/0
Extra: 01e920e61bc7546f4e05758327f5e8fe7a84de45e79e2adb454f9d537d230c1d940211000000238a2ee0d9000000000000000000

1 output(s) for total of 496.043177910000 dcy

stealth address amount amount idx
00: 930740391ff515eb96dc18766e69af57d550bbda145065692fb8dbde331c020d 496.043177910000 46169 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": 27925, "vin": [ { "gen": { "height": 27915 } } ], "vout": [ { "amount": 496043177910, "target": { "key": "930740391ff515eb96dc18766e69af57d550bbda145065692fb8dbde331c020d" } } ], "extra": [ 1, 233, 32, 230, 27, 199, 84, 111, 78, 5, 117, 131, 39, 245, 232, 254, 122, 132, 222, 69, 231, 158, 42, 219, 69, 79, 157, 83, 125, 35, 12, 29, 148, 2, 17, 0, 0, 0, 35, 138, 46, 224, 217, 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