Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afc8289e37d0338a99c93935612dfc5116687dc0de1f4e9a74dc05bfccd4cefd

Tx prefix hash: a7173c4125551980a9aae38a679a099780e7b1f594e46421f6cf259c007dda9b
Tx public key: 9349e8308508ca1aa089e160e276fcf1d12973f3897d74a6e885555db6b89b4b
Timestamp: 1723811323 Timestamp [UCT]: 2024-08-16 12:28:43 Age [y:d:h:m:s]: 00:162:21:00:21
Block: 1089155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116467 RingCT/type: yes/0
Extra: 019349e8308508ca1aa089e160e276fcf1d12973f3897d74a6e885555db6b89b4b02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5d582c62ac662aa2e69dfe4fa2e550ed0c3fe80a0c7ef24276678c37b7165e5 0.600000000000 1563774 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": 1089165, "vin": [ { "gen": { "height": 1089155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5d582c62ac662aa2e69dfe4fa2e550ed0c3fe80a0c7ef24276678c37b7165e5" } } ], "extra": [ 1, 147, 73, 232, 48, 133, 8, 202, 26, 160, 137, 225, 96, 226, 118, 252, 241, 209, 41, 115, 243, 137, 125, 116, 166, 232, 133, 85, 93, 182, 184, 155, 75, 2, 17, 0, 0, 0, 3, 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