Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7024c11168f0f1b6845d887ee8515117fe63669f133c2ebc5bc5e550cff4737f

Tx prefix hash: 70c71d344148059a8a2517ccbcbef38b9ecf6e63d88d09a79b9394e9024e4ca4
Tx public key: 86105a0e3c0a9a6252e03f1da2e5a8d799483267509ee7f01f837c9a2e1571ce
Timestamp: 1722360774 Timestamp [UCT]: 2024-07-30 17:32:54 Age [y:d:h:m:s]: 00:245:12:26:57
Block: 1077127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175361 RingCT/type: yes/0
Extra: 0186105a0e3c0a9a6252e03f1da2e5a8d799483267509ee7f01f837c9a2e1571ce02110000002191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 052df625fcb2409a222eab88038df72a65c0b87f9d764e880995bda3a2f9908d 0.600000000000 1549672 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": 1077137, "vin": [ { "gen": { "height": 1077127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "052df625fcb2409a222eab88038df72a65c0b87f9d764e880995bda3a2f9908d" } } ], "extra": [ 1, 134, 16, 90, 14, 60, 10, 154, 98, 82, 224, 63, 29, 162, 229, 168, 215, 153, 72, 50, 103, 80, 158, 231, 240, 31, 131, 124, 154, 46, 21, 113, 206, 2, 17, 0, 0, 0, 33, 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