Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 677c23ceb708ba8215c056017e9bfd9f649af0ec267e790edfef0f7190ad5976

Tx prefix hash: 9fafabe3a5837ce557ae825d0eeeb07a5c66714fb8dc36bdce10bf2ee886a2ca
Tx public key: b497e2a364e12a7aba2614e2aa1f6d0ee696ded2f7a841f55bffbb5a3472d53c
Timestamp: 1577189984 Timestamp [UCT]: 2019-12-24 12:19:44 Age [y:d:h:m:s]: 05:040:19:17:01
Block: 30684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1178947 RingCT/type: yes/0
Extra: 01b497e2a364e12a7aba2614e2aa1f6d0ee696ded2f7a841f55bffbb5a3472d53c0211000000064ac5aa02000000000000000000

1 output(s) for total of 485.659660300000 dcy

stealth address amount amount idx
00: 038d035d7e075c6a78bdc4fb8ef96c972a4a91cfc1e735722eab74b9fbc9816c 485.659660300000 50660 of 0

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": 30694, "vin": [ { "gen": { "height": 30684 } } ], "vout": [ { "amount": 485659660300, "target": { "key": "038d035d7e075c6a78bdc4fb8ef96c972a4a91cfc1e735722eab74b9fbc9816c" } } ], "extra": [ 1, 180, 151, 226, 163, 100, 225, 42, 122, 186, 38, 20, 226, 170, 31, 109, 14, 230, 150, 222, 210, 247, 168, 65, 245, 91, 255, 187, 90, 52, 114, 213, 60, 2, 17, 0, 0, 0, 6, 74, 197, 170, 2, 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