Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5116f9bab13f8907f441104d8ba68a77546a3b24f7ff08a92bf5694ff50750bc

Tx prefix hash: 8fce1c3733302d04f508e68fd7aace0b0362ae2bea4ac31af1624eaa0c1bc624
Tx public key: fb3a06cd6dbb96749b5bdb091a7724e19072b3f9a93a5b30717ee5d858591bd2
Timestamp: 1714340019 Timestamp [UCT]: 2024-04-28 21:33:39 Age [y:d:h:m:s]: 00:253:17:03:45
Block: 1010626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181606 RingCT/type: yes/0
Extra: 01fb3a06cd6dbb96749b5bdb091a7724e19072b3f9a93a5b30717ee5d858591bd202110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cfd72ec7148386f686b4498017b5c42a19e5fd6d7214a14cc224c1c349c9bd9 0.600000000000 1472636 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": 1010636, "vin": [ { "gen": { "height": 1010626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cfd72ec7148386f686b4498017b5c42a19e5fd6d7214a14cc224c1c349c9bd9" } } ], "extra": [ 1, 251, 58, 6, 205, 109, 187, 150, 116, 155, 91, 219, 9, 26, 119, 36, 225, 144, 114, 179, 249, 169, 58, 91, 48, 113, 126, 229, 216, 88, 89, 27, 210, 2, 17, 0, 0, 0, 7, 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