Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63ad835b16e679fd01750ff5cd5ca2bf0205f32a387039c3133acd0461e523be

Tx prefix hash: e454aa8821ba610a94a245d91ebbb487df2194830973b242057e2bdae3aaf6e6
Tx public key: ab729658caa4f8ed68f16c263d6897a838f875e5aecad069be04ce7e2a659441
Timestamp: 1737575880 Timestamp [UCT]: 2025-01-22 19:58:00 Age [y:d:h:m:s]: 00:147:01:30:27
Block: 1203077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104834 RingCT/type: yes/0
Extra: 01ab729658caa4f8ed68f16c263d6897a838f875e5aecad069be04ce7e2a659441021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b0def9c82a2d720af68a51caa2f8d66b830ca0f4617eec02be92076c2cb6c1f 0.600000000000 1689750 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": 1203087, "vin": [ { "gen": { "height": 1203077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b0def9c82a2d720af68a51caa2f8d66b830ca0f4617eec02be92076c2cb6c1f" } } ], "extra": [ 1, 171, 114, 150, 88, 202, 164, 248, 237, 104, 241, 108, 38, 61, 104, 151, 168, 56, 248, 117, 229, 174, 202, 208, 105, 190, 4, 206, 126, 42, 101, 148, 65, 2, 17, 0, 0, 0, 1, 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