Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e65764860d4a2c80e27477b73368da279a2e78f966bad195ef3db855e2d02f3

Tx prefix hash: 760fcc05a77b48b61c19fc32b9abb75270430b8f2a9ded4ccce202a4abcccc7d
Tx public key: bdc970d05f939c790db2e3d11d86a33a3d48dfbb6ce2f26b8f14195caa783668
Timestamp: 1718435586 Timestamp [UCT]: 2024-06-15 07:13:06 Age [y:d:h:m:s]: 00:286:23:39:18
Block: 1044596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205067 RingCT/type: yes/0
Extra: 01bdc970d05f939c790db2e3d11d86a33a3d48dfbb6ce2f26b8f14195caa783668021100000002cd63fb1b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94b5aa817a6954f76de8e99c88d03f9bfc6ffab360bf8c397b8bd5677f4c20c9 0.600000000000 1513947 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": 1044606, "vin": [ { "gen": { "height": 1044596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94b5aa817a6954f76de8e99c88d03f9bfc6ffab360bf8c397b8bd5677f4c20c9" } } ], "extra": [ 1, 189, 201, 112, 208, 95, 147, 156, 121, 13, 178, 227, 209, 29, 134, 163, 58, 61, 72, 223, 187, 108, 226, 242, 107, 143, 20, 25, 92, 170, 120, 54, 104, 2, 17, 0, 0, 0, 2, 205, 99, 251, 27, 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