Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfa96567b3420d4f0478eb8e676a6d6a0f59b343b4df708a515cae635530387e

Tx prefix hash: 45a85b4ee470785d0981a5058de39d3262b43a6327cd5ac3cbb95cdea4559f7a
Tx public key: ea6b7e1ba35424ebd9492032dd0a947319bccefa809c60420ce2c44898729d0d
Timestamp: 1735043945 Timestamp [UCT]: 2024-12-24 12:39:05 Age [y:d:h:m:s]: 00:125:21:56:16
Block: 1182163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89804 RingCT/type: yes/0
Extra: 01ea6b7e1ba35424ebd9492032dd0a947319bccefa809c60420ce2c44898729d0d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b43abd09e9f310776e2ba2d5f1dbb9b5fa389921eca3c06a9feadd2ed12f0af8 0.600000000000 1668596 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": 1182173, "vin": [ { "gen": { "height": 1182163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b43abd09e9f310776e2ba2d5f1dbb9b5fa389921eca3c06a9feadd2ed12f0af8" } } ], "extra": [ 1, 234, 107, 126, 27, 163, 84, 36, 235, 217, 73, 32, 50, 221, 10, 148, 115, 25, 188, 206, 250, 128, 156, 96, 66, 12, 226, 196, 72, 152, 114, 157, 13, 2, 17, 0, 0, 0, 3, 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