Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc3051f704cccc6bf4c5da3f355de0beef2adde7e3fa06c9f228d084ad8cbbee

Tx prefix hash: eb06dd9b9b968c1ba42dcb025439567ce117255351a368cbe8f444509e276e20
Tx public key: eac9cfe44a4db1451cdd9a25747632271b9948ccc7f02e422f8d9df647d0289a
Timestamp: 1702492019 Timestamp [UCT]: 2023-12-13 18:26:59 Age [y:d:h:m:s]: 01:183:15:59:56
Block: 912402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392378 RingCT/type: yes/0
Extra: 01eac9cfe44a4db1451cdd9a25747632271b9948ccc7f02e422f8d9df647d0289a021100000007faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c06dc18ea321e94fbd573c46126b143e198cb57237391ad513d928c45735938a 0.600000000000 1369630 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": 912412, "vin": [ { "gen": { "height": 912402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c06dc18ea321e94fbd573c46126b143e198cb57237391ad513d928c45735938a" } } ], "extra": [ 1, 234, 201, 207, 228, 74, 77, 177, 69, 28, 221, 154, 37, 116, 118, 50, 39, 27, 153, 72, 204, 199, 240, 46, 66, 47, 141, 157, 246, 71, 208, 40, 154, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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