Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb9394f193f4a6d9a6893e9d4e36a4ff99f12d57e49a13c2914c90af35b8bbda

Tx prefix hash: 9ee296f93db34b1a37443d0fda4af654b4c8ccfc7190bd6554989444bc969206
Tx public key: 88ae108c96779ce3c5eb25d0d4e2b8449c7b2b0cbc3177669f6d3f0e993ca873
Timestamp: 1712580386 Timestamp [UCT]: 2024-04-08 12:46:26 Age [y:d:h:m:s]: 01:000:13:16:57
Block: 996013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261371 RingCT/type: yes/0
Extra: 0188ae108c96779ce3c5eb25d0d4e2b8449c7b2b0cbc3177669f6d3f0e993ca87302110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3db1616e7ffa67e780db524cc0d93709866d204eba3423dcd909036cc7366479 0.600000000000 1456429 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": 996023, "vin": [ { "gen": { "height": 996013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3db1616e7ffa67e780db524cc0d93709866d204eba3423dcd909036cc7366479" } } ], "extra": [ 1, 136, 174, 16, 140, 150, 119, 156, 227, 197, 235, 37, 208, 212, 226, 184, 68, 156, 123, 43, 12, 188, 49, 119, 102, 159, 109, 63, 14, 153, 60, 168, 115, 2, 17, 0, 0, 0, 4, 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