Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f96166a55a8724b224b05369fc40a3888af067a0c118d2896d844b3e30830b2b

Tx prefix hash: 7a47c53d1c5c46842be7a96a336dcf10a746cfb5ce677096d514be228791c22e
Tx public key: 3641f5c558e3d4e18d15d311d1095d54fd9c59e2bc7f74824521181b0aa36366
Timestamp: 1657948922 Timestamp [UCT]: 2022-07-16 05:22:02 Age [y:d:h:m:s]: 02:213:08:41:14
Block: 544770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 673648 RingCT/type: yes/0
Extra: 013641f5c558e3d4e18d15d311d1095d54fd9c59e2bc7f74824521181b0aa36366021100000002faf35c9c000000000000000000

1 output(s) for total of 9.615037561000 dcy

stealth address amount amount idx
00: 1aa70b54bf7e63e3bbddf7f73dee57c5766ce1e758f08c20ee3f4a62e0e353da 9.615037561000 975587 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": 544780, "vin": [ { "gen": { "height": 544770 } } ], "vout": [ { "amount": 9615037561, "target": { "key": "1aa70b54bf7e63e3bbddf7f73dee57c5766ce1e758f08c20ee3f4a62e0e353da" } } ], "extra": [ 1, 54, 65, 245, 197, 88, 227, 212, 225, 141, 21, 211, 17, 209, 9, 93, 84, 253, 156, 89, 226, 188, 127, 116, 130, 69, 33, 24, 27, 10, 163, 99, 102, 2, 17, 0, 0, 0, 2, 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