Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d5f4a3236d3ba8aa21543567db5775138e915c0313c1baf19e45e3a2ecda760

Tx prefix hash: 3b9fc62a03643afc8ae935a5f77f4eb13e63f16fbecc44f8e20bee759b882a03
Tx public key: d57c068efdb16c614bf343260b213300ce8cbdc113bcfafa2316d8eb1ba4e6d5
Timestamp: 1763867260 Timestamp [UCT]: 2025-11-23 03:07:40 Age [y:d:h:m:s]: 00:030:19:41:52
Block: 1418107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22057 RingCT/type: yes/0
Extra: 01d57c068efdb16c614bf343260b213300ce8cbdc113bcfafa2316d8eb1ba4e6d50211000000048ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a1558531b41128fbcce324f9bc93e6c71688f15fb852499a4de878aa64d7d61 0.600000000000 1906634 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": 1418117, "vin": [ { "gen": { "height": 1418107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a1558531b41128fbcce324f9bc93e6c71688f15fb852499a4de878aa64d7d61" } } ], "extra": [ 1, 213, 124, 6, 142, 253, 177, 108, 97, 75, 243, 67, 38, 11, 33, 51, 0, 206, 140, 189, 193, 19, 188, 250, 250, 35, 22, 216, 235, 27, 164, 230, 213, 2, 17, 0, 0, 0, 4, 140, 235, 127, 9, 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