Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dea73dfb583cdc8045cf9fd4347f08f877105e01d8d6b841ec75989cd7816b1

Tx prefix hash: 0c904081d95ca5209e09b60a61c224932db7a17495b1ff44ded45e0f61edf254
Tx public key: a78bed6c02ead0c2e930beae505090b46b8da373c0bd120ddb191091b40ec7e0
Timestamp: 1741101690 Timestamp [UCT]: 2025-03-04 15:21:30 Age [y:d:h:m:s]: 00:303:06:23:45
Block: 1232037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214552 RingCT/type: yes/0
Extra: 01a78bed6c02ead0c2e930beae505090b46b8da373c0bd120ddb191091b40ec7e0021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 450524144c1de8064451eea11b0139e2628f2b58797c51dc7bc245b6a6bda288 0.600000000000 1718948 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": 1232047, "vin": [ { "gen": { "height": 1232037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "450524144c1de8064451eea11b0139e2628f2b58797c51dc7bc245b6a6bda288" } } ], "extra": [ 1, 167, 139, 237, 108, 2, 234, 208, 194, 233, 48, 190, 174, 80, 80, 144, 180, 107, 141, 163, 115, 192, 189, 18, 13, 219, 25, 16, 145, 180, 14, 199, 224, 2, 17, 0, 0, 0, 7, 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