Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 571d839f98bcd8d5f7060fa27380c5cd107441694bb80ef75d1df7709125d0a8

Tx prefix hash: 17c7934852c9e9fca0530ecd7d7d874769e5eabf9da14a4f76829aeb42e6f769
Tx public key: 384dbbf3a719201bda95425504c1a7894e954d219a68d046cf946d3e4610dee5
Timestamp: 1574756269 Timestamp [UCT]: 2019-11-26 08:17:49 Age [y:d:h:m:s]: 05:034:22:38:13
Block: 17748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1167807 RingCT/type: yes/0
Extra: 01384dbbf3a719201bda95425504c1a7894e954d219a68d046cf946d3e4610dee50211000000015ce78bfa000000000000000000

1 output(s) for total of 536.036531770000 dcy

stealth address amount amount idx
00: 8942fa9d415fe3a61dd39b42bf097c4d17b13f5636e698386cabf55a6cadbc6e 536.036531770000 26269 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": 17758, "vin": [ { "gen": { "height": 17748 } } ], "vout": [ { "amount": 536036531770, "target": { "key": "8942fa9d415fe3a61dd39b42bf097c4d17b13f5636e698386cabf55a6cadbc6e" } } ], "extra": [ 1, 56, 77, 187, 243, 167, 25, 32, 27, 218, 149, 66, 85, 4, 193, 167, 137, 78, 149, 77, 33, 154, 104, 208, 70, 207, 148, 109, 62, 70, 16, 222, 229, 2, 17, 0, 0, 0, 1, 92, 231, 139, 250, 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