Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41f3200039e121b57d5355ac565e17b418179ac954091827b4c9e73be5fec6f4

Tx prefix hash: bb1ce64dee790854fd63d14f3fd9aa02d00340cb9e616004e51d9a49633f3f49
Tx public key: 1a3486d8271b36ccfd4dd9c2d2df54a7f081d70e5b3b3bbdc12a9badf65fa858
Timestamp: 1582098322 Timestamp [UCT]: 2020-02-19 07:45:22 Age [y:d:h:m:s]: 04:321:03:06:40
Block: 67919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122059 RingCT/type: yes/0
Extra: 011a3486d8271b36ccfd4dd9c2d2df54a7f081d70e5b3b3bbdc12a9badf65fa858021100000004026b59f3000000000000000000

1 output(s) for total of 365.558566158000 dcy

stealth address amount amount idx
00: 74337f8f8fe569477feee8d138b5a1dbad8fac8877ccdbf6c084a64cef4821f2 365.558566158000 125137 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": 67929, "vin": [ { "gen": { "height": 67919 } } ], "vout": [ { "amount": 365558566158, "target": { "key": "74337f8f8fe569477feee8d138b5a1dbad8fac8877ccdbf6c084a64cef4821f2" } } ], "extra": [ 1, 26, 52, 134, 216, 39, 27, 54, 204, 253, 77, 217, 194, 210, 223, 84, 167, 240, 129, 215, 14, 91, 59, 59, 189, 193, 42, 155, 173, 246, 95, 168, 88, 2, 17, 0, 0, 0, 4, 2, 107, 89, 243, 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