Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ccfec0b6e7be6bfb23e693bf633d76eb936c36623db2e914c0d6b7160acdca3

Tx prefix hash: 5233ed7567c50eae2a90770113a120fdaab3fab8c569d8901cd548704e396c7f
Tx public key: 9f76fd88af09781b4025098acc67fb585ae4c16527a872eb48fbf54ae7842fe3
Timestamp: 1705114842 Timestamp [UCT]: 2024-01-13 03:00:42 Age [y:d:h:m:s]: 01:123:18:08:56
Block: 934123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349599 RingCT/type: yes/0
Extra: 019f76fd88af09781b4025098acc67fb585ae4c16527a872eb48fbf54ae7842fe302110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19d8649f15b371ecbc11d9e898e1c1ca9f58f144e87d675b9d2bff1001637b53 0.600000000000 1392111 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": 934133, "vin": [ { "gen": { "height": 934123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19d8649f15b371ecbc11d9e898e1c1ca9f58f144e87d675b9d2bff1001637b53" } } ], "extra": [ 1, 159, 118, 253, 136, 175, 9, 120, 27, 64, 37, 9, 138, 204, 103, 251, 88, 90, 228, 193, 101, 39, 168, 114, 235, 72, 251, 245, 74, 231, 132, 47, 227, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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