Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5faa7537abc68327e059693d5a264b6d6297491dda60b82f00aee5d2129f989

Tx prefix hash: 7ace71b00594878899c207f572d9022bd788a2842659d2ed529113db7585c643
Tx public key: 3a39967e0ff89bd7d6e51f012ca6ab69a5c5de11f0a3ba29aec21ba6af39e91f
Timestamp: 1724798735 Timestamp [UCT]: 2024-08-27 22:45:35 Age [y:d:h:m:s]: 00:224:02:13:05
Block: 1097328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160027 RingCT/type: yes/0
Extra: 013a39967e0ff89bd7d6e51f012ca6ab69a5c5de11f0a3ba29aec21ba6af39e91f02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d1e41ac9f8abdae602e692aeef81e4e3c3db3d4d52f0b1cce1c925409ab5b4a 0.600000000000 1572715 of 15

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": 1097338, "vin": [ { "gen": { "height": 1097328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d1e41ac9f8abdae602e692aeef81e4e3c3db3d4d52f0b1cce1c925409ab5b4a" } } ], "extra": [ 1, 58, 57, 150, 126, 15, 248, 155, 215, 214, 229, 31, 1, 44, 166, 171, 105, 165, 197, 222, 17, 240, 163, 186, 41, 174, 194, 27, 166, 175, 57, 233, 31, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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