Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a84a3bd1f74befb5009500db0ffebd83caac5fed0c8304406b72f98e26d074e8

Tx prefix hash: a272fc32421d3b7d79614ad09b1e73c0bca6d9fa26d5f6b737e81dc54670d438
Tx public key: 67aa2b636afd3158d4b6a563b6be87675dc23ea1632c1d23ff94333f744062c3
Timestamp: 1663051724 Timestamp [UCT]: 2022-09-13 06:48:44 Age [y:d:h:m:s]: 03:052:19:19:01
Block: 586863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 817607 RingCT/type: yes/0
Extra: 0167aa2b636afd3158d4b6a563b6be87675dc23ea1632c1d23ff94333f744062c3021100000004e6d27f9c000000000000000000

1 output(s) for total of 6.973958213000 dcy

stealth address amount amount idx
00: ff4f38c2b17e3919ddccef97fa2e2d79e8c3e98c65f8c85bff6c14ce51cbba60 6.973958213000 1021010 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": 586873, "vin": [ { "gen": { "height": 586863 } } ], "vout": [ { "amount": 6973958213, "target": { "key": "ff4f38c2b17e3919ddccef97fa2e2d79e8c3e98c65f8c85bff6c14ce51cbba60" } } ], "extra": [ 1, 103, 170, 43, 99, 106, 253, 49, 88, 212, 182, 165, 99, 182, 190, 135, 103, 93, 194, 62, 161, 99, 44, 29, 35, 255, 148, 51, 63, 116, 64, 98, 195, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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