Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e47b3df7c5da14ac87396457e33c27f82d58f4a0d3fc1ea1efd9c2e08f71e30a

Tx prefix hash: 2e503ad65496da752bf1a32307d507a36f47b52c65524da3c98c105f1341c801
Tx public key: 6b2ddc3b81adecb83499d6617784a87630e294d327dc581e784f124f54237bbc
Timestamp: 1726723842 Timestamp [UCT]: 2024-09-19 05:30:42 Age [y:d:h:m:s]: 00:202:21:33:02
Block: 1113295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144841 RingCT/type: yes/0
Extra: 016b2ddc3b81adecb83499d6617784a87630e294d327dc581e784f124f54237bbc02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43fb860384edce9471148ed389c29ee9b2bb294d6fe288ba9cc7cece94d1a45d 0.600000000000 1592918 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": 1113305, "vin": [ { "gen": { "height": 1113295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43fb860384edce9471148ed389c29ee9b2bb294d6fe288ba9cc7cece94d1a45d" } } ], "extra": [ 1, 107, 45, 220, 59, 129, 173, 236, 184, 52, 153, 214, 97, 119, 132, 168, 118, 48, 226, 148, 211, 39, 220, 88, 30, 120, 79, 18, 79, 84, 35, 123, 188, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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