Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ad11c9b643ca585f3f9d36d3d905f745a76b1fb97f1c611d52c3ddf3d955c0c

Tx prefix hash: 45b60fddd54db891eaab1f0c9028022e364ab8edf0440ad750c86d9a0dd47271
Tx public key: 542bcfb0477defb243fedbb079293db6f33b6fd931bdc286208c8432289ea613
Timestamp: 1718264551 Timestamp [UCT]: 2024-06-13 07:42:31 Age [y:d:h:m:s]: 00:337:02:40:18
Block: 1043171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240929 RingCT/type: yes/0
Extra: 01542bcfb0477defb243fedbb079293db6f33b6fd931bdc286208c8432289ea61302110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65951f48a2268dd8409db72c5a83451e8c4f13401f04ee4ebad594babab6c8b3 0.600000000000 1512260 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": 1043181, "vin": [ { "gen": { "height": 1043171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65951f48a2268dd8409db72c5a83451e8c4f13401f04ee4ebad594babab6c8b3" } } ], "extra": [ 1, 84, 43, 207, 176, 71, 125, 239, 178, 67, 254, 219, 176, 121, 41, 61, 182, 243, 59, 111, 217, 49, 189, 194, 134, 32, 140, 132, 50, 40, 158, 166, 19, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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