Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18b9df5e759b080595aeae01cad3ada56c145c18167d52a0d1d827d3f7c3c094

Tx prefix hash: 0e7e2b3dbd3dfee90db5b3eafe3828cd3c6e1231002d1ab376185036716ed0f5
Tx public key: 48b5d1190a81d91683348004d2918934f5254336b7363dc39c286355c8082789
Timestamp: 1708972782 Timestamp [UCT]: 2024-02-26 18:39:42 Age [y:d:h:m:s]: 01:038:17:25:14
Block: 966144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288694 RingCT/type: yes/0
Extra: 0148b5d1190a81d91683348004d2918934f5254336b7363dc39c286355c808278902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d3dd7df2b39b2f537a68f400d39c5756bd8ce7e788e81b8b96b32fad5efe61d 0.600000000000 1425901 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": 966154, "vin": [ { "gen": { "height": 966144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d3dd7df2b39b2f537a68f400d39c5756bd8ce7e788e81b8b96b32fad5efe61d" } } ], "extra": [ 1, 72, 181, 209, 25, 10, 129, 217, 22, 131, 52, 128, 4, 210, 145, 137, 52, 245, 37, 67, 54, 183, 54, 61, 195, 156, 40, 99, 85, 200, 8, 39, 137, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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