Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaa004629a5915185ba9850c722086b23f2e88294e603f90c05c57b718d821ae

Tx prefix hash: 470659d856248862463a85a2f7126d8c2346124103d4fc7d551d76e207ab90c1
Tx public key: f4d74eb286abcdb41fa2866a261390b46621b6fd279912e5fbe769ffb6494869
Timestamp: 1698204399 Timestamp [UCT]: 2023-10-25 03:26:39 Age [y:d:h:m:s]: 01:090:01:04:53
Block: 877070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325544 RingCT/type: yes/0
Extra: 01f4d74eb286abcdb41fa2866a261390b46621b6fd279912e5fbe769ffb6494869021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.761908849000 dcy

stealth address amount amount idx
00: a51dd7c1ee93108ebd80b03fb927fa1e3d7cf03d514ddbd56687e8127a4d74b1 0.761908849000 1332428 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": 877080, "vin": [ { "gen": { "height": 877070 } } ], "vout": [ { "amount": 761908849, "target": { "key": "a51dd7c1ee93108ebd80b03fb927fa1e3d7cf03d514ddbd56687e8127a4d74b1" } } ], "extra": [ 1, 244, 215, 78, 178, 134, 171, 205, 180, 31, 162, 134, 106, 38, 19, 144, 180, 102, 33, 182, 253, 39, 153, 18, 229, 251, 231, 105, 255, 182, 73, 72, 105, 2, 17, 0, 0, 0, 1, 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