Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa3d051edb5410d85d5b3bf37f22cbf50f266bbf223220743f7d7d3073af6c55

Tx prefix hash: 61cca80d63f6949f2f9be9df86b38745d39bfd5789a321d7959b945be439ea56
Tx public key: bc1be04a8ff14e1e9e6dd2225157350307268cb1cb9741fadd77b935c6b1189e
Timestamp: 1720370566 Timestamp [UCT]: 2024-07-07 16:42:46 Age [y:d:h:m:s]: 00:284:07:05:33
Block: 1060626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203120 RingCT/type: yes/0
Extra: 01bc1be04a8ff14e1e9e6dd2225157350307268cb1cb9741fadd77b935c6b1189e021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e041e39bdad7a0fb35d613fe0cb1a6c06f286ca6641124ed638d6427e1c39386 0.600000000000 1531111 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": 1060636, "vin": [ { "gen": { "height": 1060626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e041e39bdad7a0fb35d613fe0cb1a6c06f286ca6641124ed638d6427e1c39386" } } ], "extra": [ 1, 188, 27, 224, 74, 143, 241, 78, 30, 158, 109, 210, 34, 81, 87, 53, 3, 7, 38, 140, 177, 203, 151, 65, 250, 221, 119, 185, 53, 198, 177, 24, 158, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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