Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9f6b89884b493d05a5454597b56d9683d1e31ab6185abb5dbe8258def3e3fc5

Tx prefix hash: 1ec1bd99d25a9d1097fc95a1d0f4e9f7c24d92ab34c68cf9d2de5b5952eab57c
Tx public key: 4f1f2578c0b9898d03b66b7cea1477b0cd3e4b16cd40cf4d7b0422643cb03f5d
Timestamp: 1752454354 Timestamp [UCT]: 2025-07-14 00:52:34 Age [y:d:h:m:s]: 00:124:16:35:32
Block: 1324961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87840 RingCT/type: yes/0
Extra: 014f1f2578c0b9898d03b66b7cea1477b0cd3e4b16cd40cf4d7b0422643cb03f5d021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1045abbb0fc586db21504e82148d345b5f3c41cd39d45b980275d60f2540bbe2 0.600000000000 1812706 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": 1324971, "vin": [ { "gen": { "height": 1324961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1045abbb0fc586db21504e82148d345b5f3c41cd39d45b980275d60f2540bbe2" } } ], "extra": [ 1, 79, 31, 37, 120, 192, 185, 137, 141, 3, 182, 107, 124, 234, 20, 119, 176, 205, 62, 75, 22, 205, 64, 207, 77, 123, 4, 34, 100, 60, 176, 63, 93, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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