Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 153b4cdf2bc27d2d14975cb2671ac2c4fb2d273835c4f88b475ec1516fd5ff03

Tx prefix hash: 6a46773bcc81a01b1a8419acbb711641c02f981680a43cdc24fa2b7f2e0115a3
Tx public key: f4a722a62af0314407d52a0353e13d66602f0c765be5ed2c7f85bfce1fd86c25
Timestamp: 1705987792 Timestamp [UCT]: 2024-01-23 05:29:52 Age [y:d:h:m:s]: 01:286:22:30:08
Block: 941349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 463890 RingCT/type: yes/0
Extra: 01f4a722a62af0314407d52a0353e13d66602f0c765be5ed2c7f85bfce1fd86c250211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5cc0b0a2265bda61614e8c6576d01ff22ef5b816a6a19082d5925e8f7fa22eca 0.600000000000 1399495 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": 941359, "vin": [ { "gen": { "height": 941349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5cc0b0a2265bda61614e8c6576d01ff22ef5b816a6a19082d5925e8f7fa22eca" } } ], "extra": [ 1, 244, 167, 34, 166, 42, 240, 49, 68, 7, 213, 42, 3, 83, 225, 61, 102, 96, 47, 12, 118, 91, 229, 237, 44, 127, 133, 191, 206, 31, 216, 108, 37, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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