Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de46b294d81f132fcacecf13a8644e611026de55c861c4e0f2ed468a52d85940

Tx prefix hash: d3d8695a82c2b0e3639869d279375032008becd707e76a29de0a0e50fc10efb7
Tx public key: 36ef78c8b217c1ae4306aa85d938e18c2f7dab862f68542d9de5a082e631d0f0
Timestamp: 1751438863 Timestamp [UCT]: 2025-07-02 06:47:43 Age [y:d:h:m:s]: 00:134:23:19:47
Block: 1317050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94705 RingCT/type: yes/0
Extra: 0136ef78c8b217c1ae4306aa85d938e18c2f7dab862f68542d9de5a082e631d0f002110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bb0aff254278d162734c4fa89d5028b9a17294c89799b6515674e9bf26c729c 0.600000000000 1804715 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": 1317060, "vin": [ { "gen": { "height": 1317050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bb0aff254278d162734c4fa89d5028b9a17294c89799b6515674e9bf26c729c" } } ], "extra": [ 1, 54, 239, 120, 200, 178, 23, 193, 174, 67, 6, 170, 133, 217, 56, 225, 140, 47, 125, 171, 134, 47, 104, 84, 45, 157, 229, 160, 130, 230, 49, 208, 240, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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