Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a74c754f2c852c67dc832bc86175440c882263e8fe309be46ab74ff4c077ec9

Tx prefix hash: e76fe73bcca941ef350b24f4dbdc351fc231db3f7550a7de97aa04386af1875f
Tx public key: 2d7efcbe27029b419ddc89816faeddb0bb0e7218366887c9f8d80553c931b85a
Timestamp: 1577183737 Timestamp [UCT]: 2019-12-24 10:35:37 Age [y:d:h:m:s]: 05:022:07:43:30
Block: 30601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1166033 RingCT/type: yes/0
Extra: 012d7efcbe27029b419ddc89816faeddb0bb0e7218366887c9f8d80553c931b85a021100000072feadaf7f000000000000000000

1 output(s) for total of 485.967297868000 dcy

stealth address amount amount idx
00: a74bfe63005bd41b4ccbcef202f2e330bd73e2d49bdac28f3f5d800a55a4e6f0 485.967297868000 50531 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": 30611, "vin": [ { "gen": { "height": 30601 } } ], "vout": [ { "amount": 485967297868, "target": { "key": "a74bfe63005bd41b4ccbcef202f2e330bd73e2d49bdac28f3f5d800a55a4e6f0" } } ], "extra": [ 1, 45, 126, 252, 190, 39, 2, 155, 65, 157, 220, 137, 129, 111, 174, 221, 176, 187, 14, 114, 24, 54, 104, 135, 201, 248, 216, 5, 83, 201, 49, 184, 90, 2, 17, 0, 0, 0, 114, 254, 173, 175, 127, 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