Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82729c191cb0514b07ea19454e2faaf84e1f6c8761b4f4b2c550305798a9837e

Tx prefix hash: d464d9902cc8a47c1aafb9acc4be2d4fcc745383504d17444c7812c92294400f
Tx public key: 485573cb81d7a7a9d2c1f95e42584dbebabfb32b5e251169ed3d6571dfcb89e8
Timestamp: 1620665286 Timestamp [UCT]: 2021-05-10 16:48:06 Age [y:d:h:m:s]: 03:204:08:51:02
Block: 258256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 906403 RingCT/type: yes/0
Extra: 01485573cb81d7a7a9d2c1f95e42584dbebabfb32b5e251169ed3d6571dfcb89e8021100000363a72c95e5000000000000000000

1 output(s) for total of 85.565506831000 dcy

stealth address amount amount idx
00: 669cec7ccbe7a832a72dced1bca7b1aee4fa0e77b70cfbbafcc737d0ed4726a0 85.565506831000 543852 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": 258266, "vin": [ { "gen": { "height": 258256 } } ], "vout": [ { "amount": 85565506831, "target": { "key": "669cec7ccbe7a832a72dced1bca7b1aee4fa0e77b70cfbbafcc737d0ed4726a0" } } ], "extra": [ 1, 72, 85, 115, 203, 129, 215, 167, 169, 210, 193, 249, 94, 66, 88, 77, 190, 186, 191, 179, 43, 94, 37, 17, 105, 237, 61, 101, 113, 223, 203, 137, 232, 2, 17, 0, 0, 3, 99, 167, 44, 149, 229, 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