Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 724c71c686cb70569ca7764f46df1486c099c6ee57bfa43c64e4248466c3c3ee

Tx prefix hash: c3b716c697b3cf72c763ff5a0a638f1101cd02cd01da952df0df0cee0957ade0
Tx public key: 46d7a00879eb8725db52142baafd05a801c113040d583ac3de6735e57ef26f7f
Timestamp: 1663354298 Timestamp [UCT]: 2022-09-16 18:51:38 Age [y:d:h:m:s]: 03:045:23:47:55
Block: 589360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 812753 RingCT/type: yes/0
Extra: 0146d7a00879eb8725db52142baafd05a801c113040d583ac3de6735e57ef26f7f021100000004faf35c9c000000000000000000

1 output(s) for total of 6.842357168000 dcy

stealth address amount amount idx
00: e65d4bf9497edd0e16152c0dc2094ef1832f580e2ad9c8f4db1dc55a36ac2c6f 6.842357168000 1023649 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": 589370, "vin": [ { "gen": { "height": 589360 } } ], "vout": [ { "amount": 6842357168, "target": { "key": "e65d4bf9497edd0e16152c0dc2094ef1832f580e2ad9c8f4db1dc55a36ac2c6f" } } ], "extra": [ 1, 70, 215, 160, 8, 121, 235, 135, 37, 219, 82, 20, 43, 170, 253, 5, 168, 1, 193, 19, 4, 13, 88, 58, 195, 222, 103, 53, 229, 126, 242, 111, 127, 2, 17, 0, 0, 0, 4, 250, 243, 92, 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