Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1e1ecf996dd65478787ea74c7ae7cb2f6a8fa92d515d3b12831e6675bbb1a8f

Tx prefix hash: cd81bed7f7809a14af48b8618639b5a49c4c10a103620abc93f5ceb0638f4ea1
Tx public key: 866e4f595068c860b4b98dd03f56afb832052a49cf84c92944d369a35f670593
Timestamp: 1737258563 Timestamp [UCT]: 2025-01-19 03:49:23 Age [y:d:h:m:s]: 00:057:07:42:09
Block: 1200455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40793 RingCT/type: yes/0
Extra: 01866e4f595068c860b4b98dd03f56afb832052a49cf84c92944d369a35f670593021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 034da045e3eba815d81e035e59eb33485a9f5544d52cd7b40cbdf99093b1135e 0.600000000000 1687098 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": 1200465, "vin": [ { "gen": { "height": 1200455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "034da045e3eba815d81e035e59eb33485a9f5544d52cd7b40cbdf99093b1135e" } } ], "extra": [ 1, 134, 110, 79, 89, 80, 104, 200, 96, 180, 185, 141, 208, 63, 86, 175, 184, 50, 5, 42, 73, 207, 132, 201, 41, 68, 211, 105, 163, 95, 103, 5, 147, 2, 17, 0, 0, 0, 6, 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