Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41f44f2b3f9d548d59673ac9b45258504a1b58f21cea62649896a7e33c4996a1

Tx prefix hash: 594ad5bb2202a094fc2c09cf7ce2825624ce32e0cd2ced94833e3f12787f5033
Tx public key: 1cc848df0fd1bb49bccb76edca1c119d161005c475722a626b2c8c0f32ea5da6
Timestamp: 1712309595 Timestamp [UCT]: 2024-04-05 09:33:15 Age [y:d:h:m:s]: 01:039:02:32:02
Block: 993769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288965 RingCT/type: yes/0
Extra: 011cc848df0fd1bb49bccb76edca1c119d161005c475722a626b2c8c0f32ea5da60211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd348b8d29111167cac42386760e2605fae4a651395965a192efe7d3b1fedbdb 0.600000000000 1454157 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": 993779, "vin": [ { "gen": { "height": 993769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd348b8d29111167cac42386760e2605fae4a651395965a192efe7d3b1fedbdb" } } ], "extra": [ 1, 28, 200, 72, 223, 15, 209, 187, 73, 188, 203, 118, 237, 202, 28, 17, 157, 22, 16, 5, 196, 117, 114, 42, 98, 107, 44, 140, 15, 50, 234, 93, 166, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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