Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08ab1616b4843c41018996e6b2da750950f8f1fd5b7640132ad2a60903ab8d57

Tx prefix hash: 0d1a84ba8c9a805012c3ca761a66bafbeaf0a9f5f842a4edb2a7925be52f9d45
Tx public key: cad92b4d4ea7d4b86030e73101af1ac61df02b31e745983519337f45fdb6b8cf
Timestamp: 1712895370 Timestamp [UCT]: 2024-04-12 04:16:10 Age [y:d:h:m:s]: 01:034:19:54:06
Block: 998630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285881 RingCT/type: yes/0
Extra: 01cad92b4d4ea7d4b86030e73101af1ac61df02b31e745983519337f45fdb6b8cf02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 695d85d18d73d910c74d304e527affbe6c9aaa4a92ed3142007a77763a99ea05 0.600000000000 1459082 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": 998640, "vin": [ { "gen": { "height": 998630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "695d85d18d73d910c74d304e527affbe6c9aaa4a92ed3142007a77763a99ea05" } } ], "extra": [ 1, 202, 217, 43, 77, 78, 167, 212, 184, 96, 48, 231, 49, 1, 175, 26, 198, 29, 240, 43, 49, 231, 69, 152, 53, 25, 51, 127, 69, 253, 182, 184, 207, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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