Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcf555d8f37b989f824500f29d1f8f3907c9496d61562f9e77a473bf5ba8518e

Tx prefix hash: 3a76c06f55a60f2091fad595e0beeeb5a20115ff138ebcdcba0cabd44d45c8ea
Tx public key: 070ea951c6f92b1f4ab06700e8304a23a8a7ffab04537b90787b23e85f997583
Timestamp: 1713759767 Timestamp [UCT]: 2024-04-22 04:22:47 Age [y:d:h:m:s]: 00:206:04:27:25
Block: 1005817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147597 RingCT/type: yes/0
Extra: 01070ea951c6f92b1f4ab06700e8304a23a8a7ffab04537b90787b23e85f99758302110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc02dc08c59b9271d88771c5e40b81c92a4deaee918936871faa0ccea559dfa7 0.600000000000 1466627 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": 1005827, "vin": [ { "gen": { "height": 1005817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc02dc08c59b9271d88771c5e40b81c92a4deaee918936871faa0ccea559dfa7" } } ], "extra": [ 1, 7, 14, 169, 81, 198, 249, 43, 31, 74, 176, 103, 0, 232, 48, 74, 35, 168, 167, 255, 171, 4, 83, 123, 144, 120, 123, 35, 232, 95, 153, 117, 131, 2, 17, 0, 0, 0, 12, 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