Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46d55cc23f43f53f7196f90c68ed071f935970900e146e0673c151984cf1aa79

Tx prefix hash: afcd306f2e7cbfb30ea0d1c6339ada03eccaede8807e59839f5e1ff624b5f11b
Tx public key: 3ea096f0e6e77bd0fbf8d3741aced9fa6e223a1d1f82dc5460ad80ac19b33bc2
Timestamp: 1662168630 Timestamp [UCT]: 2022-09-03 01:30:30 Age [y:d:h:m:s]: 02:198:16:39:18
Block: 579601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 663268 RingCT/type: yes/0
Extra: 013ea096f0e6e77bd0fbf8d3741aced9fa6e223a1d1f82dc5460ad80ac19b33bc2021100000003e6d27f9c000000000000000000

1 output(s) for total of 7.371253926000 dcy

stealth address amount amount idx
00: 85827a69dc8e8ac68062c46b6bfcf0e7d8540ea5d83569845e0c18f9fd33b553 7.371253926000 1013071 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": 579611, "vin": [ { "gen": { "height": 579601 } } ], "vout": [ { "amount": 7371253926, "target": { "key": "85827a69dc8e8ac68062c46b6bfcf0e7d8540ea5d83569845e0c18f9fd33b553" } } ], "extra": [ 1, 62, 160, 150, 240, 230, 231, 123, 208, 251, 248, 211, 116, 26, 206, 217, 250, 110, 34, 58, 29, 31, 130, 220, 84, 96, 173, 128, 172, 25, 179, 59, 194, 2, 17, 0, 0, 0, 3, 230, 210, 127, 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