Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7162161ff120a83c3a3bc4278540e9902f94fc9d4f7ec8fffb257b00c9556b57

Tx prefix hash: 1c7d1090a08109ccb17608a64e5dd6f359c2c65930c2fd091bc48b5565874a28
Tx public key: 59ad5d9196e5da42e70bd6fd2ba6505a18d0fa3e87613d4e2fdb4516e508463b
Timestamp: 1737745010 Timestamp [UCT]: 2025-01-24 18:56:50 Age [y:d:h:m:s]: 00:146:11:16:45
Block: 1204469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104408 RingCT/type: yes/0
Extra: 0159ad5d9196e5da42e70bd6fd2ba6505a18d0fa3e87613d4e2fdb4516e508463b021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c968b0a2da9cfbc651073dccaa1cfb18f54893da0ff840f08efa343f134827f 0.600000000000 1691156 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": 1204479, "vin": [ { "gen": { "height": 1204469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c968b0a2da9cfbc651073dccaa1cfb18f54893da0ff840f08efa343f134827f" } } ], "extra": [ 1, 89, 173, 93, 145, 150, 229, 218, 66, 231, 11, 214, 253, 43, 166, 80, 90, 24, 208, 250, 62, 135, 97, 61, 78, 47, 219, 69, 22, 229, 8, 70, 59, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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