Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afd4f73cbd5a9ad18dc6bed601db20eea9a8a97e7d00e0a7c500489430f73d35

Tx prefix hash: 5944cf25ad661f9f3a76dc017e01a237c4a4651e11a8c2ba87b938ea30499209
Tx public key: ca1b2060d1e2e103541374a5656a5853fe7553b8af525a50e1f95c45caf85b12
Timestamp: 1736001057 Timestamp [UCT]: 2025-01-04 14:30:57 Age [y:d:h:m:s]: 00:088:21:46:16
Block: 1190085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63314 RingCT/type: yes/0
Extra: 01ca1b2060d1e2e103541374a5656a5853fe7553b8af525a50e1f95c45caf85b1202110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e76274db7e1afacab910363be29b05ebbca5ba0e6e08d86635fb68546c80ed7 0.600000000000 1676600 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": 1190095, "vin": [ { "gen": { "height": 1190085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e76274db7e1afacab910363be29b05ebbca5ba0e6e08d86635fb68546c80ed7" } } ], "extra": [ 1, 202, 27, 32, 96, 209, 226, 225, 3, 84, 19, 116, 165, 101, 106, 88, 83, 254, 117, 83, 184, 175, 82, 90, 80, 225, 249, 92, 69, 202, 248, 91, 18, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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