Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ab138504d1027b0d206394728e2a6d4575880fc7c0371cabbf3ae1467e0752a

Tx prefix hash: f346ec07566d3a05fe396d03cbac4154c64f2a7ccfb93c84c92f52d549ee19d2
Tx public key: 714c407ab89255f6d6cb0ad12292a378fbd75d08556caf6bfc16fdbfa87b3ea4
Timestamp: 1726376630 Timestamp [UCT]: 2024-09-15 05:03:50 Age [y:d:h:m:s]: 00:249:23:26:19
Block: 1110416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178530 RingCT/type: yes/0
Extra: 01714c407ab89255f6d6cb0ad12292a378fbd75d08556caf6bfc16fdbfa87b3ea4021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71d44e408b3d4b8a1ea9055d87b6229906bc758317c124fb93f7c74a5470a230 0.600000000000 1589017 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": 1110426, "vin": [ { "gen": { "height": 1110416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71d44e408b3d4b8a1ea9055d87b6229906bc758317c124fb93f7c74a5470a230" } } ], "extra": [ 1, 113, 76, 64, 122, 184, 146, 85, 246, 214, 203, 10, 209, 34, 146, 163, 120, 251, 215, 93, 8, 85, 108, 175, 107, 252, 22, 253, 191, 168, 123, 62, 164, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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