Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6be1973acc66f4e2bf3481f5912e76a5970307a806c3123d1b04304780d0f9f

Tx prefix hash: ef30d5a42e41917f42bf3fc4de0f6a55122c4417b983bac60c66c1205007a6a5
Tx public key: 2afe21d9e32459d01492c54c810026a6917d7d436c2fef6d92113952aa66a0ce
Timestamp: 1659391197 Timestamp [UCT]: 2022-08-01 21:59:57 Age [y:d:h:m:s]: 02:123:13:54:30
Block: 556661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 609734 RingCT/type: yes/0
Extra: 012afe21d9e32459d01492c54c810026a6917d7d436c2fef6d92113952aa66a0ce0211000000176570b1ef000000000000000000

1 output(s) for total of 8.781144999000 dcy

stealth address amount amount idx
00: d818185138685a15eca3a02c52e9632258371505bae985ac24597182ea4f3612 8.781144999000 988607 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": 556671, "vin": [ { "gen": { "height": 556661 } } ], "vout": [ { "amount": 8781144999, "target": { "key": "d818185138685a15eca3a02c52e9632258371505bae985ac24597182ea4f3612" } } ], "extra": [ 1, 42, 254, 33, 217, 227, 36, 89, 208, 20, 146, 197, 76, 129, 0, 38, 166, 145, 125, 125, 67, 108, 47, 239, 109, 146, 17, 57, 82, 170, 102, 160, 206, 2, 17, 0, 0, 0, 23, 101, 112, 177, 239, 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