Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44999b75dcccc40ba1c43a3e27d4cb7cd9463f99494885c79ee98838724bb071

Tx prefix hash: fb9ae14d1c78172ecab7e6116dc35f3bc5a6686b3460b08eba69ac095095731b
Tx public key: d6e1ba9eeec4ab88e531d0b1687e61faf2f0427b276cf692b7cd95afba6279a6
Timestamp: 1733880462 Timestamp [UCT]: 2024-12-11 01:27:42 Age [y:d:h:m:s]: 00:188:20:11:50
Block: 1172542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134666 RingCT/type: yes/0
Extra: 01d6e1ba9eeec4ab88e531d0b1687e61faf2f0427b276cf692b7cd95afba6279a60211000000016e963a0b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fadc41d9408267e63860a7c34690c501283be900c46118b584c46ae200660b7 0.600000000000 1658447 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": 1172552, "vin": [ { "gen": { "height": 1172542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fadc41d9408267e63860a7c34690c501283be900c46118b584c46ae200660b7" } } ], "extra": [ 1, 214, 225, 186, 158, 238, 196, 171, 136, 229, 49, 208, 177, 104, 126, 97, 250, 242, 240, 66, 123, 39, 108, 246, 146, 183, 205, 149, 175, 186, 98, 121, 166, 2, 17, 0, 0, 0, 1, 110, 150, 58, 11, 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