Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a54bd8fe61a580b30ca7ce78cfe0b8ba5df3f06cd00a0ea5689167a8a849400

Tx prefix hash: f2ef546a3284f67c0e9480493c061cd2c582dbde3ba8ec6f722e5bc2c1ca501e
Tx public key: 18608cd79376678d47e2e56e6c0458017d1801dc6a9a5ed296679d5218a00be9
Timestamp: 1740242698 Timestamp [UCT]: 2025-02-22 16:44:58 Age [y:d:h:m:s]: 00:314:10:57:00
Block: 1224909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222580 RingCT/type: yes/0
Extra: 0118608cd79376678d47e2e56e6c0458017d1801dc6a9a5ed296679d5218a00be9021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27dc949b120199f6ee8ca0413e25a69f2c8cecfc9cd79eda492fa35d57dd0f83 0.600000000000 1711772 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": 1224919, "vin": [ { "gen": { "height": 1224909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27dc949b120199f6ee8ca0413e25a69f2c8cecfc9cd79eda492fa35d57dd0f83" } } ], "extra": [ 1, 24, 96, 140, 215, 147, 118, 103, 141, 71, 226, 229, 110, 108, 4, 88, 1, 125, 24, 1, 220, 106, 154, 94, 210, 150, 103, 157, 82, 24, 160, 11, 233, 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