Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a38ef02d31a9dca18dc39381db3e8e182e1b3c8cfc22defd5001f0aae1a69d89

Tx prefix hash: 8820c4d59f0b33e121e40facf6d56e6554dcee26bba63c041015d4e63db8e313
Tx public key: 404f0dd2e2122b0a2350d02242c56ba713ec1217da9987e1ea91a691e78ca30b
Timestamp: 1684853766 Timestamp [UCT]: 2023-05-23 14:56:06 Age [y:d:h:m:s]: 01:343:20:41:40
Block: 766433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506971 RingCT/type: yes/0
Extra: 01404f0dd2e2122b0a2350d02242c56ba713ec1217da9987e1ea91a691e78ca30b02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.772105154000 dcy

stealth address amount amount idx
00: 1c27a5df062a6188b8c94163b328d4de75a4041ac3f2a6979d8f07167f4bbc3d 1.772105154000 1215474 of 0

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": 766443, "vin": [ { "gen": { "height": 766433 } } ], "vout": [ { "amount": 1772105154, "target": { "key": "1c27a5df062a6188b8c94163b328d4de75a4041ac3f2a6979d8f07167f4bbc3d" } } ], "extra": [ 1, 64, 79, 13, 210, 226, 18, 43, 10, 35, 80, 208, 34, 66, 197, 107, 167, 19, 236, 18, 23, 218, 153, 135, 225, 234, 145, 166, 145, 231, 140, 163, 11, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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