Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44a33fd2f7e9115e14938dee82c4314f895acbd63995dde189a68557e9e7fa42

Tx prefix hash: 4f426774af5d7ccbd2eb56a4f392d3cedd0f48e5035bcb1e64a1dd8cba3f2f75
Tx public key: 94a5611fb1a397d1aed1f3df88490948fd0c96d8ba4fe6b00f7a9a5818744888
Timestamp: 1719346313 Timestamp [UCT]: 2024-06-25 20:11:53 Age [y:d:h:m:s]: 00:266:15:19:49
Block: 1052127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190546 RingCT/type: yes/0
Extra: 0194a5611fb1a397d1aed1f3df88490948fd0c96d8ba4fe6b00f7a9a58187448880211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83473fee54cb1f65c2bc26d285d569255867e891bb67ba11c04aa3e6935165e7 0.600000000000 1522448 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": 1052137, "vin": [ { "gen": { "height": 1052127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83473fee54cb1f65c2bc26d285d569255867e891bb67ba11c04aa3e6935165e7" } } ], "extra": [ 1, 148, 165, 97, 31, 177, 163, 151, 209, 174, 209, 243, 223, 136, 73, 9, 72, 253, 12, 150, 216, 186, 79, 230, 176, 15, 122, 154, 88, 24, 116, 72, 136, 2, 17, 0, 0, 0, 2, 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